added harper to the dependency graph - #4

Harper v5 upgrade — completion (Path B)

This repo was already on harper@^5 (the dependency swap was done in the prior commit) but was missing the integration-testing setup. This PR completes the v5 upgrade: adds integration tests, the standard CI workflow, finishes the v4→v5 CLI/branding cleanup, and resyncs a stale lockfile.

Changes

• Integration testing: added @harperfast/integration-testing@^0.4.0, typescript, @types/node, a test:integration script, and integrationTests/app.test.ts. The tests boot the full component as a fixture under v5 and verify:
  1. the component boots and the Dog table is defined (Operations API describe_all),
  2. insert / search_by_id / delete on the Dog table,
  3. the Next.js / and /dogs pages render (HTTP 200 HTML).
  • Architecture note: the @harperfast/nextjs plugin owns the public HTTP port and routes everything to the Next.js app, so the Dog @table @export REST endpoint is not reachable over HTTP. The Next.js server actions (app/actions.js) use that table through Harper's in-process Resource API (tables.Dog); the tests drive the same data layer via the Operations API.
• harperBinPath fix (mandatory): harper's exports map only exposes ".", so the harness's auto-resolution of harper/dist/bin/harper.js throws ERR_PACKAGE_PATH_NOT_EXPORTED. The test resolves the CLI from the exported main entry and passes it explicitly as harperBinPath. (Upstream: harper should export its bin path, or the harness should resolve via the package root.)
• Lockfile resync: package.json already requested harper@^5.0.10, but package-lock.json still pinned harper@5.0.3 and carried a stale ../harper extraneous local-path entry. Resolved harper to 5.0.28, removed the stale ../harper block, and preserved harper's optional native deps (bufferutil, utf-8-validate, node-gyp-build) — a macOS npm install had dropped them, which broke npm ci on Linux. npm ci verified clean on macOS and via --os=linux dry-run (glibc + musl).
• Plugin bump: @harperfast/nextjs 2.0.0 → 2.2.1 (latest).
• CI: added .github/workflows/integration-tests.yml (Node matrix 22/24/26, actions pinned to commit hashes).
• v4→v5 CLI + branding cleanup in .github/workflows/build-and-deploy.yml: harperdb CLI → harper, @harperdb/nextjs → @harperfast/nextjs, HarperDB log/artifact names → Harper.
• README: harperdb deploy → harper deploy. Live docs.harperdb.io URLs left intact.

Migration items

This is a Next.js component that talks to Harper through the @harperfast/nextjs plugin and the Resource API (tables.Dog), via import('harper'). No v4 footprints found in source (no from 'harperdb', no blob.save(, no wasLoadedFromSource(, no harperdb-config.yaml). N/A migration items: harperdb→harper import swap (already uses import('harper')), Table.get() return-shape / frozen records (server actions only read fields off the result), transaction/context changes, child-process spawning, blob storage, and module-loading/install-script config.

Tests

Local run (npm run test:integration, --isolation=none): 4/4 pass — the single-instance isolation mode binds to 127.0.0.1, so the usual macOS multi-loopback limitation does not block it. CI (Node 22/24/26 on ubuntu-latest) is the authoritative gate; see the Integration Tests check on this PR.

Notes / flags

• The integration-test fixture boots the full component, which loads the @harperfast/nextjs plugin on startup. The plugin is not modified by this PR and boots cleanly under harper 5.0.28 + plugin 2.2.1 in local testing.
• @harperdb/code-guidelines (devDependency + prettier config) is intentionally left on the @harperdb npm scope — no @harperfast variant is published. No manual npm-scope action needed.

🤖 Generated with Claude Code